Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1537

reference
918-tree-1
name
1537
tree-preservation-order

undefined

918-tpo-1
uprn
address-text
point
POINT (-1.025553 50.868361)
geometry
MULTIPOLYGON (((-1.025440 50.868349,-1.025445 50.868372,-1.025461 50.868392,-1.025485 50.868408,-1.025517 50.868418,-1.025552 50.868422,-1.025587 50.868419,-1.025619 50.868409,-1.025645 50.868393,-1.025661 50.868373,-1.025667 50.868351,-1.025662 50.868329,-1.025646 50.868309,-1.025621 50.868293,-1.025590 50.868282,-1.025555 50.868278,-1.025520 50.868282,-1.025488 50.868291,-1.025462 50.868307,-1.025446 50.868327,-1.025440 50.868349)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL